This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
That puts me close to where I need to go. The final code is going to be much more complex but at least now I am able to select <n> docs and set some values into those docs.
Thank you so very much for the pointer to TLCC's article. Just what the doctor ordered!
<addendum>
So the larger picture is I'm trying to create a demonstation app that shows how one of our existing Notes client apps could be run on a tablet and provide improved efficiency for our quality group. Right now, they go look at a bunch of parts, decide if they're OK, then go back to their desk and issue a OK to ship record. It would be way faster if they could just do that while they're standing at the parts. They'll typically release a set of items all at one time, hence the need for processing multiple docs at one whack.
The app include a Part 11 esignature component that required the user to enter an esig password (in 3 tries or less) before the record is saved, hence the need for user input that then gets passed off for validation against the esig password database.
The TLCC form based select method leads me down a different path; I'll just add a field on the container form for the user to enter their password. Until it matches their actual password, the buttons used to process the records are hidden. The design requires a bit of JS to refresh the doc when they exit the password field and an input translation formula to keep track of how many times they've tried to enter their password.
It's probably a bit of a hack and certainly isn't very elegant, but it is quick and dirty and should work!
Thanks!
Feedback response number WEBB9BWFVU created by ~Hank Lopvelutergon on 09/26/2013